System and Method for Retrieving and Consolidating Data According to Apportionment Rules

ABSTRACT

An entity computing system for retrieving and consolidating data associated with a plurality of records for transmission to a second entity computing system is described. The entity computing system comprises a memory storing computer-executable instructions and at least one processing device. The processing device(s) receive request(s) to retrieve and consolidate data from multiple data sources associated with multiple records. The request comprises an apportionment rule indicating data to be retrieved from each of the data sources and consolidated for transmission to the second entity computing system via a secure network. The record(s) and data source(s) associated with the entity computing system are determined. Data in respect of the data source(s) associated with the entity computing system is retrieved according to the apportionment rule, stored in a consolidated data source and transmitted for receipt by the second entity computing system. Related computer-readable media and methods are also described.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority from U.S. Provisional Patent Application No. 62/402,529 filed on Sep. 30, 2016, the contents being incorporated herein by reference.

FIELD

The specification relates generally to the retrieval and consolidation of data for transmission, and specifically to systems and methods for retrieving and consolidating data in accordance with at least one apportionment rule.

BACKGROUND

Situations may arise in which a computing system associated with one entity, such as a government department, must retrieve data from a computing system associated with another entity, such as a private hospital, in order to fulfill a data request. Since the computing systems are associated with different entities, data that is accessible to the computing system associated with one entity may not be accessible to the computing system associated with the other entity. Such considerations may create technical difficulties in fulfilling requests for the retrieval and transmission of data from one entity's computing system to a computing system associated with another entity. If communications between computing systems of different entities are required to take place over secure networks performing such data retrieval and transmission activities may be more complex.

SUMMARY

In an aspect of the present application, there is provided an entity computing system for retrieving and consolidating data associated with a plurality of records for transmission to a second entity computing system. The entity computing system comprises: a memory storing computer-executable instructions, and processing device(s) coupled to the memory. The computer-executable instructions when executed by the processing device(s) cause the processing device(s) to: receive, from at least one computing device via a secure network, at least one request to retrieve and consolidate data from a plurality of data sources associated with the plurality of records, wherein each one of the plurality of data sources is associated with a respective one of the plurality of records and the request comprises an apportionment rule indicating data to be retrieved from each one of the plurality of data sources and consolidated for transmission to the second entity computing system; determine which of the plurality of records and the plurality of data sources is associated with the entity computing system; retrieve data according to the apportionment rule in respect of each one of the plurality of data sources associated with the entity computing system; store the retrieved data in a consolidated data source; and transmit, via a secure intermediary network, one of the consolidated data source and data stored in the consolidated data source for receipt by the second entity computing system.

According to some aspects, at least one of the plurality of records comprises a third entity system record and at least one of the plurality of data sources comprises a corresponding third entity system data source, and the computer-executable instructions when executed by the processing device(s) cause the processing device(s) to, in respect of each third entity system record: generate a first entity data request comprising authentication data and data indicative of the at least one request in respect of the third entity system record and corresponding third entity system data source, transmit (via either the secure intermediary network or another secure intermediary network) the first entity data request for receipt by a third entity computing system configured to access the third entity system record and the corresponding third entity system data source, receive (from the third entity computing system via either the secure intermediary network or the another secure intermediary network) third entity data of the corresponding third entity system data source responsive to the first entity data request, and store the third entity data in the consolidated data source such that the consolidated data source comprises the retrieved data and the third entity data.

According to some aspects, each one of the plurality of records comprises a transaction account, the at least one request is in respect of payment of an invoice associated with the second entity computing system, the data indicated to be retrieved from each one of the plurality of data sources by the apportionment rule comprises funds associated with each transaction account, the payment is comprised of funds from each transaction account according to the apportionment rule, the retrieved data comprises funds retrieved from the transaction accounts associated with the entity computing system, the storage of the retrieved data in the consolidated data source comprises storing the retrieved funds in a consolidated transaction account, and the transmission of the one of the consolidated data source or data stored in the consolidated data source comprises transferring the retrieved funds from the consolidated transaction account to the second entity computing system by electronic funds transfer.

According to some aspects, each one of the plurality of records comprises a transaction account in which each third entity system record corresponds to a third entity transaction account, the at least one request is in respect of payment of an invoice associated with the second entity computing system, the data indicated to be retrieved from each one of the plurality of data sources by the apportionment rule comprises funds associated with each transaction account (including the third entity transaction account), the payment is comprised of funds from each transaction account according to the apportionment rule, the retrieved data comprises funds retrieved from each of the transaction accounts associated with the entity computing system, the third entity data comprises third entity funds from the third entity transaction account, received from the third entity computing system by electronic funds transfer, the storage of the retrieved data and the third entity data in a consolidated data source comprises storing the retrieved funds and the third entity funds in a consolidated transaction account, and the transmission of the one of the consolidated data source or data stored in the consolidated data source comprises transferring the retrieved funds and third entity funds from the consolidated transaction account to the second entity computing system by electronic funds transfer.

According to some aspects, at least one of the secure intermediary network and the another secure intermediary network includes a payment network.

According to some aspects, the entity computing system further comprises a payment module, wherein the one of the consolidated data source or data stored in the consolidated data source is transmitted for receipt by the second entity computing system via the payment module.

According to some aspects, there is provided a non-transitory computer-readable medium for retrieving and consolidating data associated with a plurality of records for transmission between a first entity computing system a second entity computing system. The computer-readable medium comprises computer-executable instructions for: receiving, from at least one computing device via a secure network, at least one request to retrieve and consolidate data from a plurality of data sources associated with the plurality of records, wherein each one of the plurality of data sources is associated with a respective one of the plurality of records and the request comprises an apportionment rule indicating data to be retrieved from each one of the plurality of data sources and consolidated for transmission to the second entity computing system; determining which of the plurality of records and the plurality of data sources is associated with the entity computing system; retrieving data according to the apportionment rule in respect of each one of the plurality of data sources associated with the first entity computing system; storing the retrieved data in a consolidated data source; and transmitting, via a secure intermediary network, one of the consolidated data source or data stored in the consolidated data source for receipt by the second entity computing system.

BRIEF DESCRIPTIONS OF THE DRAWINGS

For a better understanding of the various aspects of the application described herein and to show more clearly how they may be carried into effect, reference will now be made, by way of example only, to the accompanying drawings in which:

FIG. 1 depicts a schematic of an entity system for retrieving and consolidating data associated with a plurality of records for transmission to a second entity computing system, according to non-limiting aspects of the application;

FIG. 2 depicts a schematic of an entity system for retrieving and consolidating data associated with a plurality of records for transmission to a second entity computing system, according to another set of non-limiting aspects of the application;

FIG. 3 depicts a flowchart illustrating a method of retrieving and consolidating data associated with a plurality of records for transmission between a first entity computing system and a second entity computing system in secure network communication with each other, according to non-limiting aspects of the application; and

FIG. 4 depicts an aspect of a method of retrieving and consolidating data associated with a plurality of records for transmission between a first entity computing system and a second entity computing system in secure network communication with each other, according to non-limiting aspects of the application.

DETAILED DESCRIPTION

Herein described are systems and methods for retrieving and consolidating data associated with a plurality of records for transmission between computing systems associated with different entities. It will be appreciated that for simplicity and clarity of illustration, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. In addition, numerous specific details are set forth in order to provide a thorough understanding of the exemplary aspects of the present application described herein. However, it will be understood by those of ordinary skill in the art that the exemplary aspects described herein may be practised without these specific details. In other instances, well-known methods, procedures and components have not been described in detail so as not to obscure the exemplary aspects described herein. Also, the description is not to be considered as limiting the scope of the exemplary aspects described herein. Any systems, method steps, components, parts of components, and the like described herein in the singular are to be interpreted as also including a description of such systems, method steps, components, parts of components, and the like in the plural, and vice versa.

It will also be understood that for the purposes of this application, “at least one of X, Y, and Z” or “one or more of X, Y, and Z” language can be construed as X only, Y only, Z only, or any combination of two or more items X, Y, and Z (e.g., XYZ, XYY, YZ, ZZ).

In the present application, components may be described as being “configured to” or “enabled to” perform one or more functions. Generally, it is understood that a component that is configured to or enabled to perform a function is configured to or enabled to perform the function, or is suitable for performing the function, or is adapted to perform the function, or is operable to perform the function, or is otherwise capable of performing the function.

As alluded to above, situations may arise in which a computing system associated with one entity, such as a government department, requires data from a computing system associated with another entity, such as a private hospital, to fulfill data requests. Since the two computing systems are associated with different entities, data that is accessible to the computing system(s) associated with one entity may not be accessible to the computing system(s) associated with the other entity. Such considerations may create technical difficulties in fulfilling requests for the retrieval and transmission of data from one entity's computing system and transmitted for receipt by a computing system associated with another entity. If communications between computing systems of different entities are required to take place over secure networks, and the like, performing such data retrieval and transmission tasks may be more complex.

Furthermore, a computing system associated with one entity or a governmental authority may impose particular restrictions or requirements for receiving data from computing systems associated with other entities, such as format, size and type. Those requirements may dictate that data is to be transmitted in a consolidated format, such as, for example, a single data packet or specified number of data packets.

FIG. 1 depicts first entity computing system 100 for retrieving and consolidating data for transmission to second entity computing system 102. First entity computing system 100 is associated with a first entity and second entity computing system 102 is associated with another entity (also referred to herein as a second entity). By way of non-limiting example, the first entity and second entity may comprise one or more of an organization, institution and enterprise. The data to be retrieved and consolidated is associated with a plurality of records (not shown). For example, the data to be retrieved may be associated with a plurality of property records, a plurality of inventory records for different products or a plurality of transaction accounts.

First entity computing system 100 comprises at least one memory 104 and at least one processing device 106. Memory 104 can comprise any suitable memory device, including but not limited to any suitable one of, or combination of, a local and/or remote volatile memory, non-volatile memory, random access memory (RAM), read-only memory (ROM), hard drive, optical drive, buffer(s), cache(s), flash memory, magnetic computer storage devices (e.g. hard disks, floppy disks, and magnetic tape), optical memory ((e.g., CD(s) and DVD(s)), and the like. Other suitable memory devices are within the scope of the application. As such, it is understood that the term “memory”, or any variation thereof, as used herein may comprise a tangible and non-transitory computer-readable medium (i.e., a medium which does not comprise only a transitory propagating signal per se) comprising or storing computer-executable instructions, such as computer programs, sets of instructions, code, software, and/or data for execution of any method(s), step(s) or process(es) described herein by any processing device(s) and/or microcontroller(s) described herein. Memory 104 comprises or is enabled to store computer-executable instructions 108 for execution by at least one processing device, including processing device 106.

Processing device 106 is coupled to memory 104 and is enabled to control at least some of the operations first entity computing system 100. As used herein, the terms “processing device”, “processing devices”, “processing device(s)”, “processor”, “processors” or “processor(s)” may refer to any combination of processing devices, and the like, suitable for carrying out the actions or methods described herein. For example, processing device 106 may comprise any suitable processing device, or combination of processing devices, including but not limited to a microprocessor, a central processing unit (CPU) and the like. Other suitable processing devices are within the scope of the application.

Although first entity computing system 100 is depicted as a single computing system, it is understood that according to some aspects of the application first entity computing system 100 may comprise multiple computing systems and/or computing devices in which one or more of the computing systems and/or computing devices may be remote from each other (e.g., one or more servers, mobile devices and other suitable computing devices).

First entity computing system 100 is enabled to communicate with at least one computing device 110 via secure network 112. For example, in some aspects, first entity computing system 100 comprises communication module 114 coupled to processor 106. Communication module 114 is enabled to access secure network 112 via, for example, communication link 116. Communication module 114 comprises any communication device(s) and/or application(s), or combination thereof, suitable for performing the communications with computing device 110 described herein. Communication link 116 comprises any suitable wired and/or wireless communication link(s), or suitable combination thereof. Communication module 114 is also enabled to communicate according to any suitable protocol which is compatible with secure network 112. Non-limiting examples of suitable protocols which may be compatible with secure network 112 are wireless protocols, cell-phone protocols, wireless data protocols, WiFi protocols, WiMax protocols, and/or a combination, or the like, such as Wired Equivalent Privacy (WEP), Wi-Fi Protected Access (WPA), Secure Sockets Layer (SSL) and Transport Layer Security (TLS). Communication module 114 is enabled to process data for transmission between first entity computing system 100 and computing device 110 in accordance to security protocols associated with secure network 112. For example, in some aspects, communication module 114 is enabled to encrypt data for transmission to computing device 110 and decrypt data received from computing device 110 via secure network 112. In some aspects, processing device 106 is enabled similarly to communication module 114 such that processing device 106 performs at least some of the communications with computing device 110 described herein rather than communication module 114.

Computing device 110 is enabled to access secure network 112 to communicate with first entity computing system 100. For example, computing device 110 is enabled to access secure network 112 via communication link 118. Computing device 110 may comprise a communication module suitable for performing the communications with first entity computing system 100 described herein. Communication link 118 comprises any suitable wired and/or wireless communication link(s), or suitable combination thereof. In general, computing device 110 comprises any suitable computing device, including but not limited to one or more portable electronic devices, mobile computing devices, portable computing devices, tablet computing devices, laptop computing devices, PDAs (personal digital assistants), cellphones, smartphones, computer terminals and the like. Other suitable computing devices are within the scope of the application. For the sake of simplicity a single computing device 110 is shown in FIG. 1. However, according to some aspects, more than one computing device 110 is enabled to access secure network 112 to communicate with first entity system 100 in a manner similar to computing device 110.

First entity computing system 100 is enabled to access a plurality of data sources, such as two or more of data source 120-1, data source 120-2 and data source 120-3 (referred to collectively as data sources 120 or plurality of data sources 120, and individually as data source 120-1, data source 120-2, data source 120-3). Data sources 120 are associated with the plurality of records and each one of data sources 120 is associated with a respective one of the plurality of records. For example, if the plurality of records comprises records 1 to 3, then each one of the plurality of data sources 120-1 to 120-3 corresponds to each one of the plurality of records (e.g., data source 120-1 corresponds to record 1, data source 120-2 corresponds to record 2, data source 120-3 corresponds to record 3). Data sources 120 comprise any suitable type of data source or combination thereof. For example, in some aspects, data sources 120 comprises one or more of a data structure, a database, a data storage device and a data file. In some aspects of the application, at least one of data sources 120 is remote from first entity computing system 100. In some aspects, first entity computing system 100 is enabled to access data sources in addition to data sources 120.

In accordance with computer-executable instructions 108, processing device 106 is enabled to receive, from computing device 110 via secure network 112, at least one request 122 to retrieve and consolidate data from data sources 120. Request 122 is in any format suitable for processing by processing device 106. Request 122 comprises an apportionment rule that indicates data that is to be retrieved from each one of data sources 120. For example, the apportionment rule may indicate that a first data portion 124-1 is to be retrieved from data source 120-1, a second data portion 124-2 is to be retrieved from data source 120-2 and a third data portion 124-3 is to be retrieved from data source 120-3. The apportionment rule also indicates that the retrieved data (e.g., first data portion 124-1, second data portion 124-2 and third data portion 124-3) is to be consolidated for transmission from first entity computing system 100 to second entity computing system 102. For example, second entity computing system 102 may be configured to receive data associated with the request 122 as a consolidated data packet. Additionally, transmitting data retrieved from data sources 120 in consolidated form as opposed to separate transmissions of data from each one of data sources 120 may reduce processing time and drain on processing resources of first entity system 100 in managing data requests, such as request 122.

In accordance with computer-executable instructions 108, processing device 106 is enabled to determine which of the plurality of records and the plurality of data sources of request 122 is associated with first entity computing system 100. In some aspects, as discussed further below, at least one of the plurality of records is associated with a third entity computing system and at least one of the plurality of data sources of request 122 is a corresponding third entity system data source. In such aspects, first entity computing system 100 is unable to access the corresponding third entity data source. For example, the corresponding third entity computing system may control retrieval and transmission of data from the corresponding data source. Additional discussion about such aspects is provided further below.

It is also understood that, according to some aspects, each one of the plurality of records and the plurality of data sources of the request(s) are associated with the third entity.

Returning to FIG. 1, processing device 106 may determine which of the plurality of records and the plurality of data sources 120 is associated with first entity computing system 100 using a variety of means. For example, first entity computing system 100 may be a computing system of a medical clinic and each one of the plurality of records may be medical records of patients of the medical clinic, and data source 120-1, data source 120-2, data source 120-3 may comprise data pertaining to those patients. However, in some aspects, request 122 may comprise an indication that one or more portions of the data to be retrieved from data sources 120 is associated with either a third entity record and a third entity data source. In some aspects, the apportionment rule comprises such an indication.

Processing device 106 is further enabled to retrieve data according to the apportionment rule in respect of each one of data sources 120 that is associated with first entity computing device 100. For example, processing device 106 may determine that each one of data sources 120, data source 120-1, data source 120-2 and data source 120-3, is associated with first entity computing device 100. The apportionment rule of request 122 may indicate that a first data portion 124-1 is to be retrieved from data source 120-1, a second data portion 124-2 is to be retrieved from data source 120-2 and a third data portion 124-3 is to be retrieved from data source 120-3.

According to some aspects, processing device 106 is enabled to, prior to retrieving first data portion 124-1, second data portion 124-2 and third data portion 124-3, determine a first data source state of each one of data sources 120 associated with first entity computing system 100 and whether the determined first data source state conflicts with the apportionment rule of request 122. According to some aspects, the first data source state may comprise an indication of at least one of a data format, a data size and a data type associated with each one of data sources 120. For example, processing device 106 may be enabled to determine at least one data retrieval parameter indicated in the apportionment rule, such as a data format, a data size and data type of the data to be retrieved from each one of the plurality of data sources, such as data sources 120, according to request 122. The processing device 106 may then interrogate each one of data sources 120 for data indicative of a first data source state corresponding to the at least one data retrieval parameter. For example, according to some aspects, if the at least one data retrieval parameter comprises a requested data size for each one of first data portion 124-1, second data portion 124-2 and third data portion 124-3, then in response to the interrogation by processing device 106 in respect of a current size of data stored at each one of data sources 120, data source 120-1, data source 120-2 and data source 120-3 may each return an interrogation response comprising an indication of a current size of data stored at the respective one of data sources 120.

According to some aspects, if processing device 106 determines that first data source state conflicts with the apportionment rule of request 122 (e.g., current size of data of any one of data sources 120 conflicts with the respective requested data size), then processing device 106 may generate and transmit alert data 126 for receipt by computing device 110 via secure network 112. Alert data 126 may comprise an alert message for display at a Graphical User Interface (GUI) of computing system 110. According to some aspects, processing device 106 may wait for alert response data 128 from computing device 110 indicative of a response to alert data 126 before proceeding to retrieve data from data sources 120. In some aspects, alert response data 128 comprises a revised request to retrieve and consolidate data from data sources 120.

According to some aspects, after retrieving the requested data (e.g., first data portion 124-1, second data portion 124-2 and third data portion 124-3), processing device 106 is enabled to determine a second data source state of each one of data sources 120 associated with first entity computing system 100. According to some aspects, processing device 106 stores the determined second data source state of each one of data sources 120 associated with first entity computing system 100 at memory 104 or another suitable device, module or data source. For example, according to some aspects, at least one reconciliation data source, such as reconciliation data source 130, may be accessible to first entity computing system 100 such that processing device 106 is enabled to store data indicative of the determined second data source state and/or state change data indicative of any changes between the first data source state and the second data source state for one or more of data sources 120 in reconciliation data source 130. According to some aspects, reconciliation data source 130 comprises one or more of a data structure, a database, a data storage device and a data file.

Processing device 106 is enabled to store the retrieved data, first data portion 124-1, second data portion 124-2 and third data portion 124-3 in the present non-limiting aspect, in consolidated data source 132. Consolidated data source 132 comprises any suitable type of data source or combination thereof. According to some aspects, consolidated data source 132 comprises one or more of a data structure, a database, a data storage device and a data file. Although consolidated data source 132 is depicted as a data source separate from data sources 120 and reconciliation data source 130, according to some aspects one or more of data sources 120 and reconciliation data source 130 comprise consolidated data source 132 (or data to be stored in consolidated data source). According to some aspects, data to be stored at consolidated data source 132 is stored at a data source that may also store other data. For example, according to some aspects, at least one of data source 120-1, data source 120-2 and data source 120-3 comprises consolidated data source 132 (or data stored in consolidated data source).

Processing device 106 is enabled to transmit, via secure intermediary network 134, one of the consolidated data source 132 or data stored in the consolidated source 132 for receipt by second entity computing system 102 according to any suitable protocol which is compatible with secure intermediary network 134. Non-limiting examples of suitable protocols compatible with secure intermediary network 134 are wireless protocols, cell-phone protocols, wireless data protocols, WiFi protocols, WiMax protocols, and/or a combination, or the like, such as Wired Equivalent Privacy (WEP), Wi-Fi Protected Access (WPA), Secure Sockets Layer (SSL) and Transport Layer Security (TLS). Suitable communication protocols for secure intermediary network 134 may be based on or dictated by, for example, the type of data being transmitted between first entity computing system 100 and second entity computing system 102, the type of entity associated with either first entity computing system 100 or second entity computing system 102, system requirements or data transmission policies of first entity computing system 100 and second entity computing system 102, and/or policies of a relevant governmental authority. According to some aspects, one of the consolidated data source 132 or data stored in the consolidated source 132 is transmitted via communication module 114, or other computing module of first entity computing system 100 suitable for transmitting one of the consolidated data source 132 or data stored in the consolidated source 132 via secure intermediary network 134.

First entity computing system 100 and second entity computing system 102 communicate with each other via secure intermediary network 134 using communication links 136 and 138. Communication links 136 and 138 comprise any suitable wired and/or wireless communication link(s), or suitable combination thereof.

Attention is directed to FIG. 2, which depicts a first entity computing system 200 for retrieving and consolidating data associated with a plurality of records for transmission to second entity computing system 102, according to another exemplary aspect of the application and in which like or similar elements are denoted by like or similar numbers in FIG. 1. For simplicity and ease of understanding, discussion of the systems and devices depicted in FIG. 2 will focus on certain similarities and differences from those depicted in FIG. 1.

Similar to first entity computing system 100, first entity computing system 200 comprises memory 104 coupled to processing device 106. Memory 104 stores computer-executable instructions 208 which is similar to computer-executable instructions 108, aside from the differences described further below. First entity computing system 200 is also enabled to access a plurality of data sources 120 associated with a plurality of records.

However, first entity computing system 200 is also enabled to communicate with a computing system associated with a third entity, such as third entity computing system 240, via secure intermediary network 242 according to any protocol compatible with second secure intermediary network 242 and suitable for communications between first entity computing system 200 and third entity computing system 240. According to some aspects, the communication protocols for second secure intermediary network 242 may be similar to the communication protocols for secure intermediary network 134. Communications between first entity computing system 200 and third entity computing system 240 via second secure intermediary network 242 utilize communication links 244 and 246. Communication links 244 and 246 comprise any suitable wired and/or wireless communication link(s), or suitable combination thereof.

According to some aspects, third entity computing system 240 is enabled to communicate with first entity computing system 200 via secure intermediary network 134 and/or second secure intermediary network 242.

Third entity computing system 240 is associated with third entity system record(s) (not shown). The third entity system record(s) is associated with at least one corresponding third entity data source, such as corresponding third entity data source 248, that is accessible and/or controlled by third entity computing system 240. In other words, third entity computing system 240 is configured to access the third entity system record and corresponding third entity system data source(s) 248. To be understood, corresponding third entity system data source(s) 248 is not accessible to or controlled by first entity computing system 200.

Similarly to first entity computing system 100, processing device 106 of first entity computing system 200 is enabled to receive, from computing device 110 via secure network 112, requests to retrieve and consolidate data from a plurality of data sources associated with a plurality of data records in accordance with computer-executable instructions stored at memory 104. In accordance with computer-executable instructions 208, processing device 106 may be enabled to receive request 222 from computing device 110 to retrieve and consolidate data from a plurality of data sources associated with a plurality of data records, in which at least one of the plurality of records includes a third entity system record and at least one of the plurality of data sources includes a corresponding third entity system data source, such as third entity system data source(s) 248.

Similarly to request 122, request 222 comprises an apportionment rule indicating data to be retrieved from each one of the plurality of data sources, such as data source 120-1, data source 120-2, data source 120-3 and corresponding third entity data source 248, and consolidated for transmission to second entity computing system 102. Processing device 106 is also enabled to, in accordance with computer-executable instructions 208, to determine which of the plurality of records and the plurality of data sources is associated with first entity computing system 200 in a manner similar to that described in reference to first entity computing system 100 and computer-executable instructions 108. According to some aspects of the application, processing device 106 is enabled to, in accordance with computer-executable instructions 208, to determine which of the plurality of records and the plurality of data sources is associated with third entity system record(s) and corresponding third entity system data source(s) 248. According to some aspects, request 222 may comprise an indication that one or more portions of the data to be retrieved from the plurality of data sources, data source 120-1, data source 120-2, data source 120-3 and corresponding third entity data source 248, is associated with third entity records(s) and/or corresponding third entity data source 248. In some aspects, the apportionment rule comprises such an indication.

For example, the apportionment rule of request 222 may indicate that first data portion 124-1 is to be retrieved from data source 120-1, second data portion 124-2 is to be retrieved from data source 120-2, third data portion 124-3 is to be retrieved from data source 120-3 and a fourth data portion 250 is to be retrieved from third entity computing system 240 and/or corresponding third entity data source 248.

Since corresponding third entity data source 248 is inaccessible or otherwise outside the control of first entity computing system 200, first entity computing system 200 must request fourth data portion 250 from third entity computing system 240. Processing device 106 is enabled to, according to computer-executable instructions 208, generate a first entity data request 252 comprising authentication data and data indicative of request 222 in respect of third entity system record(s) and third entity record(s) and/or corresponding third entity system data source 248. The authentication data comprises any data suitable for authenticating request 222 to third entity computing system 240 in respect of the third entity. According to some aspects, the authentication data may comprise credentials associated with computing device 110, a profile associated with computing device 110 and/or received by a suitable input device of computing device 110 that are associated with at least one of the third entity system record(s) and corresponding third entity system data source 248.

According to computer-executable instructions 208, processing device 106 is enabled to transmit first entity data request 252 via second secure intermediary network 242 for receipt by third entity computing system 240. Processing device 106 is also enabled to receive, from third entity computing system 240 via second secure intermediary network 242, third entity data of corresponding third entity system data source 248 responsive to first entity data request 252, such as fourth data portion 250. Processing device 106 is further enabled to store the third entity data of corresponding third entity system data source 248, fourth data portion 250 in the present example, in consolidated data source 132 such that the consolidated data source comprises the data retrieved from data sources 120 (associated with first entity computing system 200) and the third entity data, such as fourth data portion 250.

Similarly to first entity system 100, processing device 106 of the exemplary aspect depicted in FIG. 2 is enabled to transmit, via secure intermediary network 134, one of the consolidated data source 132 or data stored in the consolidated source 132 for receipt by second entity computing system 102.

Attention is now directed to FIGS. 3 and 4 which depict a flowchart of a method 300 of retrieving and consolidating data associated with a plurality of records for transmission between a first entity computing system and a second entity computing system in secure network communication with each other, according to non-limiting aspects of the application. In order to assist in the explanation of method 300, it will be assumed that method 300 is performed using either first entity computing system 100 or first entity computing system 200, as indicated. Furthermore, the following discussion of method 300 will lead to a further understanding of first entity computing system 100 and first entity computing system 200, and the various components of those systems. However, it is to be understood that first entity computing system 100, first entity computing system 200 and/or method 300 can be varied, and need not work exactly as discussed herein in conjunction with each other, and that such variations are within the scope of present implementations.

It is appreciated that, in some aspects, method 300 is implemented by first entity computing system 100 or first entity computing system 200 by processing device 106. Indeed, method 300 is one way in which first entity computing system 100 or first entity computing system 200 may be configured. It is to be emphasized, however, that method 300 need not be performed in the exact sequence as shown, unless otherwise indicated; and likewise various blocks may be performed in parallel rather than in sequence; hence the elements of method 300 are referred to herein as “blocks” rather than “steps”. It is also to be understood, however, that method 300 can be implemented on variations of first entity computing system 100 and first computing system 200 as well.

At block 302, at least one processing device of first entity computing system 100 or first entity computing system 200, such as processing device 106, receives at least one request, such as request 122 or request 222, to retrieve and consolidate data from a plurality of data sources associated with a plurality of records. As discussed above, according to some aspects, the plurality of data records may be associated with data sources 120. According to some aspects, the plurality of data records may be associated with data sources 120 and data source 248.

The request(s) to retrieve and consolidate data comprises an apportionment rule that indicates data to be retrieved from each one of the plurality of data sources and consolidated for transmission to the second entity computing system, such as second entity computing system 102.

At block 304, the at least one processing device, such as processing device 106, determines which of the plurality of records and plurality of data sources is associated with the first entity computing system. According to some aspects, processing device 106 determines that data sources 120 (data source 120-1, data source 120-2 and data source 120-3) are associated with the first entity computing system 100.

As discussed above, according to some aspects, at least one of the plurality of records may be a third entity system record and at least one of the plurality of data sources is a corresponding third entity system data source, such as corresponding third entity system data source 248. Referring to FIG. 4, at block 306, in respect of each third entity system record, processing device 106 generates a first entity data request, such as first entity data request 252, comprising authentication data and data indicative of the at least one request, such as request 222, in respect of the third entity system record and corresponding third entity system data source, such as corresponding third entity system data source 248.

At block 308, in respect of each third entity system record, the at least one processing device, such as processing device 106, transmits the first entity data request, such as first entity data request 252, for receipt by a third entity computing system configured to access the third entity system record and the corresponding third entity system data source, such as third entity computing system 240 configured to access corresponding third entity system data source 248. According to some aspects, first entity data request 252 is transmitted via second secure intermediary network 242. According to some aspects, as discussed above, third entity computing system 240 is configured to communicate with first entity computing system 200 via secure intermediary network 134, and first entity data request 252 is transmitted via secure intermediary network 134.

At block 310, in respect of each third entity system record, the at least one processing device, such as processing device 106, receives third entity data of the corresponding third entity system data source responsive to the first entity data request. For example, according to some aspects, processing device 106 receives fourth data portion 250 of corresponding third entity system data source 248, which is responsive to first entity data request 252. According to some aspects, processing device 106 receives third entity data via second secure intermediary network 242. According to some aspects, processing device 106 receives the third entity data, such as fourth data portion 250, via secure intermediary network 134.

At block 312, the at least one processing device, such as processing device 106, stores the third entity data in a consolidated data source. For example, according to some aspects, processing device 106 stores fourth data portion 250 in consolidated data source 132.

Referring to FIG. 3, at block 314, the at least one processing device retrieves data according to the apportionment rule in respect of data sources associated with the first entity computing system. For example, according to some aspects, processing device 106 retrieves first data portion 124-1, second data portion 124-2 and third data portion 124-3 from data source 120-1, data source 120-2 and data source 120-3, respectively.

At block 316, the at least one processing device stores the data retrieved in accordance with the apportionment rule in a consolidated data source. For example, according to some aspects, processing device 106 stores first data portion 124-1, second data portion 124-2 and third data portion 124-3 in consolidated data source 132. For example, according to some aspects, processing device 106 stores first data portion 124-1, second data portion 124-3, third data portion 124-3 and fourth data portion 250 at consolidated data source 132 such that the data stored at consolidated data source comprises data retrieved from data sources 120 and third entity system data source 248.

At block 318, at least one processing device transmits, via the secure intermediary network, one of the consolidated data source and the data stored in the consolidated data source for receipt by the second entity computing system. For example, according to some aspects, processing device 106 transmits first data portion 124-1, second data portion 124-2 and third data portion 124-3. For example, according to some aspects, processing device 106 transmits first data portion 124-1, second data portion 124-3, third data portion 124-3 and fourth data portion 250.

According to some aspects, the at least one processing device transmits one of the consolidated data source and the data stored in the consolidated data source to an intermediary module enabled to transmit data, via the secure intermediary network, from the first entity computing system for receipt by the second entity computing system. According to some aspects, the intermediary module may perform additional processing to the consolidated data source or data stored in the consolidated data source prior to transmission via the secure intermediary network for receipt by the second entity computing system. Such additional processing may, according to some aspects, be performed to enhance the suitability of the data to be transmitted via the secure intermediary network for receipt by the second entity computing system. By way of non-limiting example, the additional processing may comprise one or more of encryption and compression. For example, according to some aspects, communication module 114 is enabled to transmit data, via the secure intermediary network 134, for receipt by second entity computing system 102. According to some related aspects, processing device 106 transmits one of the consolidated data source 132 and the data stored in the consolidated data source 132 to communication module 114, which transmits the received one of the consolidated data source 132 and the data stored in the consolidated data source 132 via secure intermediary network 134. According to some related aspects, communication module 114 comprises at least one processing device suitable configured to carry out such communication tasks.

The systems, devices and methods described herein are applicable in a variety of contexts in which management of data transmission between multiple computing systems associated with multiple separate entities is to be performed. As such, it is understood that the aspects described below are non-limiting and that the technical advantages of the described systems, devices and methods may be realized in a variety of data management contexts and applications.

Referring to FIGS. 1 and 2, according to some aspects, first entity computing system 100 and first entity computing system 200 are computing system(s) operated by a financial institution, such as a bank, and second entity computing system 102 is a computing system operated by an entity separate from the financial institution, such as a merchant, utility provider or government entity, and which issues at least one invoice for payment by a user with access to or who is otherwise associated with computing device 110 (also referred to herein as an “issuing entity”).

According to some aspects, request 122 and request 222 are in respect of payment of an invoice associated with the second entity computing system 102. The payment of the invoice is comprised of funds from each one of the plurality of transaction accounts according to the respective apportionment rule. As discussed above, request 122 and request 222 each comprise a request to retrieve and consolidate data from a plurality of data sources associated with a plurality of records. According to some aspects, each one of the plurality of records comprises a transaction account, such as a debit card, a credit card account, a checking account and a line of credit account, and each one of the data sources is associated with each transaction account provided by the first entity, such as data source 120. For example, according to some aspects, data source 120-1 is associated with a debit card account, data source 120-2 is associated with a credit card account and data source 120-3 is associated with a checking account associated with the first entity and which are transaction accounts held by a user with access to or who otherwise associated with computing device 110.

According to some aspects, at least one of the transaction accounts is associated with a third entity. For example, according to some aspects, third entity computing system 240 is operated by another financial institution, separate from the financial institution of the first entity, and corresponding third entity system data source 248 is associated with a line of credit provided to the user by the other financial institution.

The data indicated by request 122 and request 222 to be retrieved from the transaction account(s) according to the apportionment rule comprises funds associated with each transaction account indicated in the respective request. The apportionment rule may comprise an indication of the respective amounts to be withdrawn or drawn against each one of the transaction account(s). For example, in respect of request 122, the apportionment rule may comprise an indication to retrieve funds associated with transaction accounts provided only by the first entity, such as the debit card account associated with data source 120-1, the credit card account associated with data source 120-2 and the checking account associated with data source 120-3. As another example, in respect of request 222, the apportionment rule may comprise an indication to retrieve funds associated with transaction accounts provided by both the first entity and the second entity, such as the debit card account associated with data source 120-1, the credit card account associated with data source 120-2, the checking account associated with data source 120-3 and the line of credit associated with corresponding third entity system data source 248. Additionally, the apportionment rule may comprise an indication of the respective amounts to be withdrawn or drawn against each one of the transaction accounts indicated in request 122 or request 222.

According to some aspects, the data retrieved in accordance with the apportionment rule comprises funds to be retrieved from the transaction accounts associated with the first entity computing system 100, first entity computing system 200 and, in respect of the apportionment rule of request 222, also comprises funds to be retrieved from the transaction account(s) associated with the third entity computing system 240 (also referred to herein as “third entity funds”). In respect of request 222, since the funds to be retrieved from the transaction account(s) associated with corresponding third entity system data source 248 are to be retrieved from an entity computing system separate from first entity computing system 200, the third entity data provided in response to the first entity data request 252, such as fourth data portion 250, comprises funds from the third entity transaction account transferred by Electronic Funds Transfer (ETF), such as Direct Deposit and/or Interac™ e-transfer, or any other suitable manner of transferring the third entity funds for receipt by first entity computing system 200.

According to some aspects, storing the retrieved data and/or the third entity data in a consolidated data source comprises storing the funds retrieved from the transaction account(s) according to the apportionment rule in a consolidated transaction account, such as in least one consolidated transaction account associated with consolidated data source 132. According to some aspects, consolidated data source 132, and the at least one consolidated transaction account, is not a separate data source or transaction account, but comprises a portion or subset of another data source or transaction account. For example, according to some aspects, funds that are to be stored in the at least one consolidated transaction account as described above are stored in a central account of the first entity or a ledger account associated with treasury funds of the first entity. In other words, according to some aspects, the data to be stored at consolidated data source 132 (e.g., the retrieved data and/or the third entity data) and the funds to be stored in the at least one consolidated transaction account (e.g., the retrieved funds and/or the third entity funds) are stored in at least one other data source or transaction account operated by the first entity that is not necessarily dedicated to only storing the retrieved data and/or the third entity data or the retrieved funds and/or third entity funds. According to some related aspects, the retrieved data and/or the third entity data, or the retrieved funds and/or third entity funds, are stored with an indication that the data or funds are to be transmitted or transferred as a consolidated payment or a consolidated data transmission (e.g., single data packet).

According to some aspects, the transmission of the one of the consolidated data source or data stored in the consolidated data source comprises transferring the retrieved funds and/or third entity funds from the consolidated transaction account to the second entity computing system by ETF, or other any other suitable manner of transferring the retrieved funds and/or third entity funds for receipt by second computing entity system 102. For example, in respect of request 122, first data portion 124-1, second data portion 124-2 and third data portion 124-3 comprise funds retrieved in accordance with the apportionment rule and stored at a consolidation transaction account associated with consolidated data source 132. Transmitting first data portion 124-1, second data portion 124-2 and third data portion 124-3 via secure network 134 for receipt by second entity computing system 102 may comprise transferring funds from the consolidated transaction account(s) to second entity computing system 102 by ETF.

As discussed above, one of the consolidated data source 132 or data stored in the consolidated source 132 may be transmitted via communication module 114, or another suitable computing module of first entity computing system 100, for receipt by second entity computing system 102 via secure intermediary network 134. According to some aspects, communication module 114, or the other suitable computing module described above, may comprise a payment module enabled to process and transmit data in respect of payments of invoices from an issuing entity via secure intermediary network 134.

According to some aspects, at least one of secure intermediary network 134 and second secure intermediary network 242 is a payment network that may be enabled to transmit data associated with payments to second entity computing system 102. For example, at least one of secure intermediary network 134 and second secure intermediary network 242 may comprise or otherwise be enabled to access an Automated Clearing House (ACH) network or other network(s) suitable and/or specifically enabled to receive, track and/or transmit data associated with payments. At least one of secure intermediary network 134 and second secure intermediary network 242 may operate in accordance with laws and/or guidelines associated with at least one relevant governmental authority in compliance with which one or more of first entity computing system 100, first entity computing system 200 may operate.

As discussed above, according to some aspects, processing device 106 is enabled to store data indicative of the determined second data source state and/or state change data indicative of any changes between the first data source state and the second data source state for one or more of data sources 120 in reconciliation data source 130. For example, according to some aspects, the first data source state may comprise an indication of an amount of the funds available at each transaction account associated with data sources 120, and the second data source state may comprise an indication of an amount of the funds available at each transaction account associated with data sources 120 after the retrieval of first data portion 124-1, second data portion 124-2 and third data portion 124-3, and the funds associated therewith. According to some aspects, state change data stored at reconciliation data source 130 comprises an indication of changes in the amount of funds available at the transaction account(s) associated with first entity computing system 100, first entity computing system 200, which may assist in generating data for a ledger of the first entity.

Those skilled in the art will appreciate that in some implementations, the functionality of first entity computing system 100, first entity computing system 200 and method 300 can be implemented using pre-programmed hardware or firmware elements (e.g., application specific integrated circuits (ASICs), electrically erasable programmable read-only memories (EEPROMs), etc.), or other related components. In other implementations, the functionality of first entity computing system 100, first entity computing system 200 and method 300 can be achieved using a computing apparatus that has access to a code memory (not shown) which stores computer-readable program code for operation of the computing apparatus. The computer-readable program code could be stored on a computer readable storage medium which is fixed, tangible and readable directly by these components, (e.g., removable diskette, CD-ROM, ROM, fixed disk, USB drive). Furthermore, it is appreciated that the computer-readable program can be stored as a computer program product comprising a computer usable medium. Further, a persistent storage device can comprise the computer readable program code. It is yet further appreciated that the computer-readable program code and/or computer usable medium can comprise a non-transitory computer-readable program code and/or non-transitory computer usable medium. Alternatively, the computer-readable program code could be stored remotely but transmittable to these components via a modem or other interface device connected to a network (including, without limitation, the Internet) over a transmission medium. The transmission medium can be either a non-mobile medium (e.g., optical and/or digital and/or analog communications lines) or a mobile medium (e.g., microwave, infrared, free-space optical or other transmission schemes) or a combination thereof.

Persons skilled in the art will appreciate that there are yet more alternative aspects and modifications possible, and that the above examples are only illustrations of one or more aspects of the application. The scope, therefore, is only to be limited by the claims appended hereto. 

What is claimed is:
 1. An entity computing system for retrieving and consolidating data associated with a plurality of records for transmission to a second entity computing system, the entity computing system comprising: a memory storing computer-executable instructions, and at least one processing device coupled to the memory, the computer-executable instructions when executed by the at least one processing device causing the at least one processing device to: receive, from at least one computing device via a secure network, at least one request to retrieve and consolidate data from a plurality of data sources associated with the plurality of records, wherein each one of the plurality of data sources is associated with a respective one of the plurality of records and the request comprises an apportionment rule indicating data to be retrieved from each one of the plurality of data sources and consolidated for transmission to the second entity computing system; determine which of the plurality of records and the plurality of data sources is associated with the entity computing system; retrieve data according to the apportionment rule in respect of each one of the plurality of data sources associated with the entity computing system; store the retrieved data in a consolidated data source; and transmit, via a secure intermediary network, one of the consolidated data source and data stored in the consolidated data source for receipt by the second entity computing system.
 2. The entity computing system of claim 1, wherein at least one of the plurality of records includes a third entity system record and at least one of the plurality of data sources includes a corresponding third entity system data source, and the computer-executable instructions when executed by the at least one processing device cause the at least one processing device to: in respect of each said third entity system record, generate a first entity data request comprising authentication data and data indicative of the at least one request in respect of the third entity system record and the corresponding third entity system data source, transmit, via either the secure intermediary network or another secure intermediary network, the first entity data request for receipt by a third entity computing system configured to access the third entity system record and the corresponding third entity system data source, receive, from the third entity computing system via either the secure intermediary network or the another secure intermediary network, third entity data of the corresponding third entity system data source responsive to the first entity data request, and store the third entity data in the consolidated data source such that the consolidated data source comprises the retrieved data and the third entity data.
 3. The entity computing system of claim 1, wherein the computer-executable instructions when executed by the at least one processing device cause the at least one processing device to: in respect of each one of the plurality of data sources associated with the entity computing system: prior to the retrieval, determine a first data source state and whether the first data source state conflicts with the apportionment rule.
 4. The entity computing system of claim 3, wherein the computer-executable instructions when executed by the at least one processing device cause the at least one processing device to: in respect of each one of the plurality of data sources associated with the entity computing system: after the retrieval, determine a second data source state.
 5. The entity computing system of claim 1, wherein: each one of the plurality of records comprises a transaction account; the at least one request is in respect of payment of an invoice associated with the second entity computing system; the data indicated to be retrieved from each one of the plurality of data sources by the apportionment rule comprises funds associated with each transaction account; the payment is comprised of funds from each transaction account according to the apportionment rule; the retrieved data comprises funds retrieved from the transaction accounts associated with the entity computing system; the storage of the retrieved data in the consolidated data source comprises storing the retrieved funds in a consolidated transaction account; and the transmission of the one of the consolidated data source or data stored in the consolidated data source comprises transferring the retrieved funds from the consolidated transaction account to the second entity computing system by electronic funds transfer.
 6. The entity computing system of claim 2, wherein: each one of the plurality of records comprises a transaction account in which each third entity system record corresponds to a third entity transaction account; the at least one request is in respect of payment of an invoice associated with the second entity computing system; the data indicated to be retrieved from each one of the plurality of data sources by the apportionment rule comprises funds associated with each transaction account, including the third entity transaction account; the payment is comprised of funds from each transaction account according to the apportionment rule; the retrieved data comprises funds retrieved from each of the transaction accounts associated with the entity computing system; the third entity data comprises third entity funds from the third entity transaction account, received from the third entity computing system by electronic funds transfer; the storage of the retrieved data and the third entity data in a consolidated data source comprises storing the retrieved funds and the third entity funds in a consolidated transaction account; and the transmission of the one of the consolidated data source or data stored in the consolidated data source comprises transferring the retrieved funds and third entity funds from the consolidated transaction account to the second entity computing system by electronic funds transfer.
 7. The entity computing system of claim 2, wherein at least one of the secure intermediary network and the another secure intermediary network includes a payment network.
 8. The entity computing system of claim 5 further comprising a payment module, wherein the one of the consolidated data source or data stored in the consolidated data source is transmitted for receipt by the second entity computing system via the payment module.
 9. The entity computing system of claim 6 further comprising a payment module, wherein the one of the consolidated data source or data stored in the consolidated data source is transmitted for receipt by the second entity computing system via the payment module.
 10. The entity computing system of claim 3, wherein the first data source state comprises an indication of at least one of a data type and size of data associated with each one of the plurality of data sources.
 11. The entity computing system of claim 1, wherein the at least one computing device comprises a mobile computing device.
 12. A non-transitory computer-readable medium for retrieving and consolidating data associated with a plurality of records for transmission between a first entity computing system a second entity computing system, the computer-readable medium comprising computer-executable instructions for: receiving, from at least one computing device via a secure network, at least one request to retrieve and consolidate data from a plurality of data sources associated with the plurality of records, wherein each one of the plurality of data sources is associated with a respective one of the plurality of records and the request comprises an apportionment rule indicating data to be retrieved from each one of the plurality of data sources and consolidated for transmission to the second entity computing system; determining which of the plurality of records and the plurality of data sources is associated with the entity computing system; retrieving data according to the apportionment rule in respect of each one of the plurality of data sources associated with the first entity computing system; storing the retrieved data in a consolidated data source; and transmitting, via a secure intermediary network, one of the consolidated data source or data stored in the consolidated data source for receipt by the second entity computing system.
 13. The non-transitory computer-readable medium of claim 12, wherein at least one of the plurality of records includes a third entity system record and at least one of the plurality of data sources includes a corresponding third entity system data source, the computer-readable medium further comprising computer-executable instructions for: in respect of each third entity system record, generating a first entity data request comprising authentication data and data indicative of the at least one request in respect of the third entity system record and corresponding third entity system data source, transmitting, via either the secure intermediary network or another secure intermediary network, the first entity data request for receipt by a third entity computing system configured to access the third entity system record and the corresponding third entity system data source, receiving, from the third entity computing system via either the secure intermediary network or the another secure intermediary network, third entity data of the third entity system data source responsive to the first entity data request, and storing the third entity data in the consolidated data source such that the consolidated data source comprises the retrieved data and the third entity data.
 14. A method of retrieving and consolidating data associated with a plurality of records for transmission between a first entity computing system and a second entity computing system in secure network communication with each other, the method comprising: via a processing device of the first entity computing system: receiving, from at least one computing device via a secure network, at least one request to retrieve and consolidate data from a plurality of data sources associated with the plurality of records, wherein each one of the plurality of data sources is associated with a respective one of the plurality of records and the request comprises an apportionment rule indicating data to be retrieved from each one of the plurality of data sources and consolidated for transmission to the second entity computing system; determining which of the plurality of records and the plurality of data sources is associated with the first entity computing system; retrieving data according to the apportionment rule in respect of each one of the plurality of data sources associated with the first entity computing system; storing the retrieved data in a consolidated data source; and transmitting, via a secure intermediary network, one of the consolidated data source or data stored in the consolidated data source for receipt by the second entity computing system.
 15. The method of claim 14, wherein at least one of the plurality of records comprises a third entity system record and at least one of the plurality of data sources comprises a corresponding third entity system data source, the method further comprising: in respect of each said third entity system record, generating a first entity data request comprising authentication data and data indicative of the at least one request in respect of the third entity system record and the corresponding third entity system data source, transmitting, via either the secure intermediary network or another secure intermediary network, the first entity data request for receipt by a third entity computing system configured to access the third entity system record and the corresponding third entity system data source, receiving, from the third entity computing system via either the secure intermediary network or the another secure intermediary network, third entity data of the corresponding third entity system data source responsive to the first entity data request, and storing the third entity data in the consolidated data source such that the consolidated data source comprises the retrieved data and the third entity data.
 16. The method of claim 14 further comprising: in respect of each one of the plurality of data sources associated with the first entity computing system: prior to the retrieving, determining a first data source state and whether the first data source state conflicts with the apportionment rule.
 17. The method of claim 16 further comprising: in respect of each one of the plurality of data sources associated with the first entity computing system: after the retrieving, determining a second data source state.
 18. The method of claim 14, wherein: each one of the plurality of records comprises a transaction account; the at least one request is in respect of payment of an invoice associated with the second entity computing system; the data indicated to be retrieved from each one of the plurality of data sources by the apportionment rule comprises funds associated with each transaction account; the payment is comprised of funds from each transaction account according to the apportionment rule; the retrieved data comprises funds retrieved from the transaction accounts associated with the first entity computing system; storing the retrieved data in the consolidated data source comprises storing the retrieved funds in a consolidated transaction account; and transmitting the one of the consolidated data source or data stored in the consolidated data source comprises transferring the retrieved funds from the consolidated transaction account to the second entity computing system by electronic funds transfer.
 19. The method of claim 15, wherein: each one of the plurality of records comprises a transaction account in which each third entity system record corresponds to a third entity transaction account; the at least one request is in respect of payment of an invoice associated with the second entity computing system; the data indicated to be retrieved from each one of the plurality of data sources by the apportionment rule comprises funds associated with each transaction account, including the third entity transaction account; the payment is comprised of funds from each transaction account according to the apportionment rule; the retrieved data comprises funds retrieved from each of the transaction accounts associated with the first entity computing system; the third entity data comprises third entity funds from the third entity transaction account, received from the third entity computing system by electronic funds transfer; the storage of the retrieved data and the third entity data in the consolidated data source comprises storing the retrieved funds and the third entity funds in a consolidated transaction account; and the transmission of the one of the consolidated data source or data stored in the consolidated data source comprises transferring the retrieved funds and third entity funds from the consolidated transaction account to the second entity computing system by electronic funds transfer.
 20. The method of claim 15, wherein at least one of the secure intermediary network and the another secure intermediary network comprises a payment network. 